I suspect this will once again cause invalid args assertion error as described in my comment in #2932

Fair. I'll have a look.

In #2932 I'm using

```diff

+        if (proposedCursorPosition.X > bufferSize.Width() - 1)
+       
+            proposedCursorPosition.X = bufferSize.Width() - 1;
+        }
+
         // This section is essentially equivalent to `AdjustCursorPosition`
         // Update Cursor Position
         cursor.SetPosition(proposedCursorPosition);

I didn't really know which one is correct between 0 and bufferSize.Width() - 1. Guess that #3277 ruled out 0.

I wonder if the assertion triggers in cases where #1360 would have already triggered? Where we are at the righthand side of the screen with one half of a double-width character that shouldn't have been put there?

Yeah it appears to be the same issue. Only that #1360 happens in release build, where assertion doesn't trigger, I think.

With #3292 fixing #3277 by fully reverting both and #2965, #2932, should this PR be closed?

Do we also need to re-open the original PRs/issues?

#2965 closed #2986, and apparently fixed a crash introduced by #2932

#2932 closed #2713

Yep, thanks!